Skip to content

Use WorkManager for Android Notification Scheduling - #17

Open
singhaditya21 wants to merge 1 commit into
mainfrom
android-notification-workmanager-3912692864281811005
Open

Use WorkManager for Android Notification Scheduling#17
singhaditya21 wants to merge 1 commit into
mainfrom
android-notification-workmanager-3912692864281811005

Conversation

@singhaditya21

Copy link
Copy Markdown
Owner

This change replaces the unreliable CoroutineScope.launch based scheduling for daily morning briefings with Android's WorkManager (specifically leveraging the existing WorkScheduler and DailySummaryWorker).

Key changes:

  • NotificationService.kt:
    • Replaced scheduleMorningBriefing implementation to call WorkScheduler.scheduleDailySummary.
    • Updated sendDailyBriefing to support dynamic content (summary, temperatures, precipitation chance) passed from the worker.
    • Added overloads for alert methods (sendRainAlert, sendSevereWeatherAlert, sendUVWarning) to match the signatures used by WeatherWorker and DailySummaryWorker, ensuring type safety and correct behavior.
    • Removed unused coroutine dependencies within the service.

This ensures notifications are reliably scheduled even if the app is killed or the device restarts (handled by WorkManager and BootReceiver which presumably reschedules work).


PR created automatically by Jules for task 3912692864281811005 started by @singhaditya21

Replaced unreliable coroutine-based scheduling in `scheduleMorningBriefing` with `WorkManager` via `WorkScheduler`.
Updated `sendDailyBriefing` to accept optional weather parameters for dynamic notification content.
Added overloads for `sendRainAlert`, `sendSevereWeatherAlert`, and `sendUVWarning` to align with `WeatherWorker` usage.
Removed unused coroutine imports and scope.

Co-authored-by: singhaditya21 <53948039+singhaditya21@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@singhaditya21

Copy link
Copy Markdown
Owner Author

Leaving this open rather than merging, for two reasons worth recording.

The Android app cannot currently be built. android/gradle/wrapper/gradle-wrapper.jar is absent from the repo — not gitignored, just never committed — so ./gradlew fails from a fresh clone. Until that is regenerated (cd android && gradle wrapper --gradle-version 8.13) there is no way to compile or test this change, and CI has no Android job either. Merging unverifiable platform code into main is not worth the risk while the backend work is landing there.

Everything else in this triage pass was either applied to main with tests or closed with a reason; these Android PRs are the one group blocked on tooling rather than on review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant